Mobile network operator (MNO) control of WiFi QoS via EAP/diameter

ABSTRACT

A mobile network operator (MNO) may control WiFi QoS. 3GPP has specified control mechanisms for various levels of quality of service (QoS) over the cellular access and core network. Embodiments described herein provide differentiation of WiFi QoS based on MNO requirements. In particular, extensible authentication protocol (EAP) and diameter messages may be extended to include a wireless local area network QoS parameter. This may be used by user equipment to set the uplink 802.11e User Priority (UP) for offloaded or evolved packet core-routed WiFi traffic.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a National Stage Application filed under 35 U.S.C.371 of International Application No. PCT/US2014/055859, filed Sep. 16,2014, which claims the benefit of U.S. Provisional Patent Ser. No.61/878,260, filed Sep. 16, 2013, the disclosure of which is herebyincorporated by reference as if set forth in its entirety herein.

BACKGROUND

3GPP standards for cellular and WiFi interworking have been availablesince Release 6, evolving in Release 8, and expanding in subsequentreleases. Institute of Electrical and Electronics Engineers (IEEE) hasalso ratified the 802.11u standard, Amendment for “Interworking withExternal Networks” which addresses wireless local area network (WLAN)enhancements in subscription service provider networks (SSPNs), such asthose operated by 3GPP MNOs. However, feature deployment has beenlimited even though these standards enable access to operator-providedservices and mobility between cellular and WiFi.

Mobile network operators (MNOs) may provide subscribers with managednetwork access using both cellular and WiFi technologies. Currently,MNOs typically consider WiFi only as a way to offload Internet-basedtraffic for their dual-mode subscribers. In current approaches, an MNOmay configure certain handset applications to always use WiFi forInternet access when WiFi is available. For example, an MNO mayconfigure applications to use WiFi when the applications are in lowmobility scenarios and while they are within a WiFi hotspot. Currentapproaches to using WiFi may reduce congestion on the MNO's cellular andcore networks, but the reduced congestion may come with a cost.

SUMMARY

Described herein are methods, devices, and systems for MNO control ofWiFi quality of service (QoS). In one embodiment in which a systemcomprises a user equipment (UE) and an mobile network operator (MNO), aQoS parameter may be inserted into a diameter message, whereby the UE isprovided with QoS policies that are specified by the MNO. In accordancewith another embodiment, a UE sets a user priority for wireless localarea network uplink traffic flows according to a policy of the MNO. Forexample, the policy may be pre-configured or may be signaled bymechanisms described herein. Different WiFi QoS may be provided based onMNO requirements.

In an example embodiment, a server, for instance a trusted wirelessaccess network (TWAN) server, may receive a message that indicates awireless local area network (WLAN) quality of service (QoS) parameter.The message may be formatted in accordance with an extended diametermessage. The server may insert the WLAN QoS parameter into an extendedextensible authentication protocol (EAP) message, thereby providing aQoS policy specified by an MNO to the UE. Further, the TWAN server maysend a diameter message to a second server. The diameter message may beindicative of an identity of the UE. The TWAN server may monitorextensible authentication protocol (EAP) messages between the UE and thesecond server. Based on the monitored EAP messages and the identity ofthe UE, the TWAN server may identify the WLAN QoS policy associated withthe UE. The TWAN server may send the identified WLAN QoS policy to theUE, for instance via an extended EAP message.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with accompanying drawingswherein:

FIG. 1 illustrates an architecture for trusted wireless local areanetwork (WLAN) access to evolved packet core (EPC);

FIG. 2 is a flow diagram for controlling a WiFi quality of service (QoS)based on global policy in accordance with an example embodiment;

FIGS. 3A-D is a flow diagram that for controlling a WiFi QoS based onsubscriber policy in accordance with example embodiments;

FIG. 4A illustrates an example architecture for trusted wireless localarea network (WLAN) access and LTE EPC in which one or more disclosedembodiments may be implemented;

FIG. 4B is a system diagram of an example user equipment (UE) or otherdevice that may be used within the communication system illustrated inFIG. 4A; and

FIG. 4C is a block diagram of an example computing system in whichaspects of the communication system of FIG. 4A may be embodied.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The ensuing detailed description is provided to illustrate exemplaryembodiments and is not intended to limit the scope, applicability, orconfiguration of the invention. Various changes may be made in thefunction and arrangement of elements and steps without departing fromthe spirit and scope of the invention.

Integrated small cell and WiFi (ISW) networks are deployments of smallcells in the licensed spectrum along with WiFi access points in theunlicensed spectrum. Mobile Network Operators (MNOs) are beginning toincorporate “carrier-grade” WiFi in ways that complement their cellularand core networks through cost-effective integration and interworking.This may drive development of a variety of network architectures,subscriber service options, and policy management mechanisms.

ISW network requirements may address lower cost alternatives forInternet traffic offload via WiFi, service continuity between cellularand WiFi, simplified network deployment and management (e.g., viaconsolidation of cellular and WiFi provisioning mechanisms andself-organizing network (SON) extensions), and enhanced policy-basedmulti-access traffic management (e.g., via dynamic traffic steering andlocal enforcement of quality of service (QoS) across cellular and WiFiaccess technologies).

Disclosed herein are solutions for MNO control of WLAN QoS viaExtensible Authentication Protocol (EAP) and Diameter messages. If MNOsdeploy carrier WiFi, there may be a desire for access points (APs) andsubscriber handsets to support at least some 802.11e or WiFi Alliance(WFA) Wireless Multimedia (WMM) QoS features so that the MNOs can offervalue-added services via different levels of QoS over WiFi. For uplinkdata (WiFi transmission from the UE) a mechanism can be defined forproviding operator-specified QoS policies to the user equipment (UE)directly from a 3GPP AAA server. The UE may also use these MNO policiesto request a specified QoS level for specific downlink traffic streamsfrom a wireless local area network (WLAN) AP.

To give further context, discussed below are relevant WiFi standards forWLANs QoS and WLANs as associated with 3GPP. 3GPP has specified controlmechanisms for various levels of QoS over the cellular access and corenetwork. As detailed herein, these capabilities are extended to includedifferentiation of WLAN QoS based on MNO requirements as may besimilarly applied to cellular access networks.

WiFi may be used for inexpensive delivery of MNO value-added packet dataservices, including mobile session continuity, via unlicensed spectrum.Adjustments may be made for delivering better QoS for offloaded WiFitraffic depending on how and where the offload is done. For instance,WLANs may support QoS differentiation using the WMM standards based onIEEE 802.11e. IEEE 802.11e refers to Amendment 8: Medium Access Control(MAC) Quality of Service Enhancements. Applications using the WMM APIscan prioritize 802.11e MAC frames according to user priorities (UPs)mapped to access categories (ACs) for voice, video, best effort, orbackground. The four AC queues allow higher priority frames to betransmitted with a statistically lower wait time than lower priorityframes.

FIG. 1 illustrates a simplified architecture for a Trusted WLAN accessnetwork (TWAN) connected with an EPC. Further details regarding the TWANare discussed with regard to FIG. 4A thru FIG. 4C. According to section16.1.1 of TS 23.402, when the WLAN is considered trusted by theoperator, TWAN 101 interfaces with EPC 119 in multiple ways. TWAN 101may interface with EPC 119 via STa interface 104 for authenticationprocedures with 3GPP AAA server 107. STa interface 104 securelytransports access authentication, authorization, mobility parameters andcharging-related information. In addition, TWAN 101 may interface withEPC 119 via S2a interface 106 for bearer management procedures withpacket data network (PDN) gateway (PGW) 108. ANDSF server 114 may belocated in EPC 119 and communicate with UE 102 via communicativelyconnected PGW 108. ANDSF server 114 may communicate to UE 102 using ans14 interface 100. ANDSF server 114 may initiate a push to distributeits information to UE 102 or UE 102 may query ANDSF server 114 to pulldesired information.

TS 23.402 considers the detailed functional split within TWAN 101 as outof scope for 3GPP. The external behavior exposed by the SWw interface105, S2a interface 106, and STa interface 107 are considered in scopefor 3GPP. Nevertheless, functions such as WLAN AN 113, Trusted WLANAccess Gateway (TWAG) 117, and Trusted WLAN AAA Proxy (TWAP) 115 areassumed in scope of TWAN 101. WLAN AN 113 consists of one or more WLANAccess Points (APs). An AP terminates the UE's WLAN IEEE 802.11 link viaSWw interface 105. These could be standalone APs or APs connected to aWireless LAN Controller (WLC), e.g., using IETF CAPWAP/DTLS protocols.

TWAG 117 acts as the default IP router for UE 102 on its access link andterminates the GTP-based S2a interface 106 with the PGW 108. It alsoacts as a DHCP server for UE 102. TWAG 117 maintains a UE MAC addressassociation for forwarding packets between UE 102 and TWAG 117 via apoint-to-point link through the AP (not shown) in WLAN 113 and the S2aGTP-u tunnel for UE 102 toward PGW 108. The implementation of thepoint-to-point link, including how and when it is setup, is out-of-scopeof 3GPP (e.g., WiFi procedures are defined by the WiFi Alliance and IEEE802.11, while WiFi network discovery and selection decisions are basedon UE implementation).

TWAP 115 terminates the Diameter-based STa interface 104 with 3GPP AAAServer 107. Diameter refers to the IETF authentication, authorization,and accounting protocol. TWAP 115 relays the AAA information betweenWLAN AN 113 and 3GPP AAA Server 107 (or Proxy in case of roaming). TWAP115 establishes the binding of UE 102 subscription data includinginternational mobile subscriber identity (IMSI) with UE 102 MAC addressand can inform TWAG 117 of layer 2 attach and detach events. There maybe an analogy drawn to 3GPP “attach” which can be viewed as an“authentication” procedure with the core network. TWAP 115 may alsoprovide TWAG 117 with subscription information for UE 102, such as IMSIor MAC bindings.

The 3GPP Release 11 SA2 work item for “S2a Mobility Over GTP” (SaMOG)has focused on enabling a GPRS tunneling protocol (GTP)-based S2ainterface between PGW 108 and TWAN 101. The 3GPP Release 11architectures, functional descriptions, and procedures for GTP-based S2aover Trusted WLAN access were standardized in section 16 of TS 23.402.The applicable GTP control plane protocol for tunnel management(GTPv2-C) is specified in TS 29.274 and the GTP user plane is specifiedin TS 29.281. A focus of SaMOG is “trusted access to the EPC,” hence,the procedures begin with an “initial attachment” to EPC 101. Just as inLTE, successful completion of the initial attach procedure results inestablishment of a “default” EPC 101 bearer enabling an “always-on”connection with the core network via a GTP tunnel on S2a interface 106.For SaMOG, direct offload to the Internet 111 is not relevant, becausein the situation of direct offload to the Internet 111 the user planeconnection to EPC 119 is bypassed and no GTP tunnels are established.Home subscriber server (HSS) 109 or 3GPP AAA server 107 may indicate viaSTa interface 104 whether access to EPC 119 via S2a interface 106 or theuse of non-seamless WLAN offload (NSWO) or both are allowed for asubscriber.

UE 102 initiates an “initial attach” with TWAN 101 using “TWAN-specificL2 procedures” that are outside the scope of 3GPP. For WLAN, this wouldbe via IEEE 802.11 procedures followed by the IETF EAPoL-Start messagethat initiates EAP procedures with the 3GPP AAA server 107 through TWAP115. By comparison, initiation of an “initial attach” for 3GPP access isdone via establishment of an RRC connection with an evolved node B (eNB)followed by 3GPP-specified non-access stratum (NAS) signaling with amobility management entity (MME).

After standard EAP-based authentication, TWAP 115 provides TWAG 117 withthe default access point name (APN) retrieved from HSS subscription datavia 3GPP AAA server 107. TWAG 117 then selects PGW 108 associated withthe APN and sends a GTP-C “Create Session Request” to PGW 108. Thisrequest identifies the RAT type as “Non-3GPP” and includes the DefaultEPS Bearer QoS (as passed down from HSS 109) and a GTP Tunnel EndpointIdentifier (TEID) for TWAN 101. Note that this QoS is applicable to theGTP tunnel between the TWAG 117 and PGW 108 (S2a interface 106) not tothe actual end-to-end EPS bearer which includes the WiFi link, where theWLAN radio interface is considered out of scope for 3GPP. The defaultbearer QoS includes a QoS Class Identifier (QCI) for a non-guaranteedbit rate (non-GBR). The QCI value represents a resource type (GBR ornon-GBR), priority level, packet delay budget, and packet error lossrate, as shown in Table 1 which reflects information from Table 3.9, pg.57 of “Next Generation Mobile Communications Ecosystem: TechnologyManagement for Mobile Communications by Saad Z. Asif.

TABLE 1 Standardized QCI Characteristics Packet Delay Packet ErrorResource Budget Loss Rate QCI Type Priority (NOTE 1) (NOTE 2) ExampleServices 1 GBR 2 100 ms 10⁻² Conversational Voice (NOTE 3) 2 4 150 ms10⁻³ Conversational Video (NOTE 3) (Live Streaming) 3 3  50 ms 10⁻³ RealTime Gaming (NOTE 3) 4 5 300 ms 10⁻⁶ Non-Conversational Video (NOTE 3)(Buffered Streaming) 5 Non- 1 100 ms 10⁻⁶ IMS Signalling (NOTE 3) GBR 66 300 ms 10⁻⁶ Video (Buffered Streaming) (NOTE 4) TCP-Based (e.g., www,e-mail, chat, ftp, p2p file sharing, progressive video, etc.) 7 7 100 ms10⁻³ Voice, (NOTE 3) Video (Live Streaming) Interactive Gaming 8 8 300ms 10⁻⁶ Video (Buffered Streaming) (NOTE 5) TCP-Based (e.g., www,e-mail, 9 9 chat, ftp, p2p file sharing, (NOTE 6) progressive video,etc.) [1] (NOTE 1): A delay of 20 ms for the delay between a PCEF and aradio base station should be subtracted from a given PDB to derive thepacket delay budget that applies to the radio interface. This delay isthe average between the case where the PCEF is located “close” to theradio base station (roughly 10 ms) and the case where the PCEF islocated “far” from the radio base station, e.g., in case of roaming withhome routed traffic (the one-way packet delay between Europe and the USwest coast is roughly 50 ms). The average takes into account thatroaming is a less typical scenario. It is expected that subtracting thisaverage delay of 20 ms from a given PDB will lead to desired end-to-endperformance in most typical cases. Also, note that the PDB defines anupper bound. Actual packet delays - in particular for GBR traffic -should typically be lower than the PDB specified for a QCI as long asthe UE has sufficient radio channel quality. [2] (NOTE 2): The rate ofnon-congestion related packet losses that may occur between a radio basestation and a PCEF should be regarded to be negligible. A PELR valuespecified for a standardized QCI therefore applies completely to theradio interface between a UE and radio base station. [3] (NOTE 3): ThisQCI is typically associated with an operator controlled service, i.e., aservice where the SDF aggregate's uplink/downlink packet filters areknown at the point in time when the SDF aggregate is authorized. In caseof E-UTRAN this is the point in time when a corresponding dedicated EPSbearer is established/modified. [4] (NOTE 4): If the network supportsMultimedia Priority Services (MPS) then this QCI could be used for theprioritization of non-real-time data (i.e., most typically TCP-basedservices/applications) of MPS subscribers. [5] (NOTE 5): This QCI couldbe used for a dedicated “premium bearer” (e.g., associated with premiumcontent) for any subscriber/subscriber group. Also in this case, the SDFaggregate's uplink/downlink packet filters are known at the point intime when the SDF aggregate is authorized. Alternatively, this QCI couldbe used for the default bearer of a UE/PDN for “premium subscribers.”[6] (NOTE 6): This QCI is typically used for the default bearer of aUE/PDN for non-privileged subscribers. Note that AMBR can be used as a“tool” to provide subscriber differentiation between subscriber groupsconnected to the same PDN with the same QCI on the default bearer.

PGW 108 returns a “Create Session Response” to TWAG 117 including thedefault EPS Bearer QoS, the allocated UE 102 IP address, and a TEID forPGW 108. A GTP-U tunnel now exists between TWAG 117 and PGW 108. Packetsfor this EPS bearer are subsequently encapsulated with a GTPv1-U headercontaining the destination TEID, a UDP header identifying GTPv1-U portnumber 2152, and an “outer IP” header marked with DSCP valuescorresponding to the QCI. The DSCP mappings are established based onoperator policies.

PGW 108 may also initiate creation of dedicated bearers on the GTP-basedS2a interface. TWAN 101 specific resource allocation/modificationprocedure may be executed in this step in order to support the dedicatedbearer QoS. The details of this step are out of the scope of 3GPP.

PGW 108 may also initiate a bearer modification procedure for aGTP-based S2a bearer. This procedure is used to update the TFT for anactive default or dedicated S2a bearer, or in cases when one or severalof the S2a bearer QoS parameters QCI, GBR, MBR or ARP are modified(including the QCI or the ARP of the default S2a bearer), e.g. due tothe HSS Initiated Subscribed QoS Modification procedure.

The IPv4 address and/or IPv6 prefix is allocated to UE 102 when a newPDN connection is established. For instance, TWAG 117 may request anIPv4 address in the GTP Create Session Request and the IPv4 address isdelivered to TWAG 117 during the GTP tunnel establishment via the GTPCreate Session Response from PGW 108. When UE 102 requests the IPv4address via DHCPv4, TWAG 117 delivers the received IPv4 address, subnetmask, default route, DNS server name, etc., to UE 102 within DHCPv4signaling. UE 102 can use the subnet mask and the default gatewayaddress for its packet routing decisions. Corresponding procedures arealso defined for IPv6. For the case of NSWO, it is assumed TWAN 101 cansupport a network address translation (NAT) function and can provide theUE with a local IP address.

For Trusted WLAN access to EPC 119, the PDN connectivity service isprovided by the point-to-point connectivity between UE 102 and TWAN 101concatenated with S2a bearer(s) between TWAN 101 and PGW 108.

The S2a bearers include a default bearer as a minimum. When the defaultbearer is modified and/or when dedicated bearers are established, TFTscontaining packet filters are also provided. TWAN 101 handles uplinkpackets based on the uplink packet filters in the TFTs received from PGW108 for the S2a bearers of the PDN connection. Downlink packets arehandled by PGW 108 based on downlink packet filters in the TFTs storedin PGW 108 for the S2a bearers of the PDN connection.

IEEE 802.11e has standardized two mechanisms for providing QoSenhancements in WLANs, namely, EDCA and HCCA. Subsequently, the WiFiAlliance has adopted some features of the 802.11e EDCA standard intotheir Wireless MultiMedia (WMM) certification program. The use of thesestandards have been limited, mostly focused on vendor-specificenterprise deployments (e.g., for voice over WLAN). It has not typicallybeen used for interworking with 3GPP MNO QoS policies.

IEEE 802.11e includes MAC capabilities for QoS prioritization in WLANswhere transmission opportunities (TXOPs) are determined based on trafficpriority. Mechanisms have been standardized using a hybrid coordinationfunction (HCF) in the AP. The HCF may be described as a “hybrid”function because it supports both 1) contention-based channel access(enhanced distributed channel access—EDCA), and 2) controlled channelaccess (HCF controlled channel access—HCCA). EDCA is a prioritizedCSMA/CA contention-based access mechanism. EDCA maps user priorities(UP) to four “access categories” (ACs) allowing higher priority framesto be transmitted with a statistically lower wait time than lowerpriority frames. The backoff value for each AC is broadcast by theQoS-enabled AP in the beacon frames for use by stations in uplinktransmissions. HCF Controlled Channel Access (HCCA) is a contention-freeaccess mechanism based on AP polling mechanisms. Although this cantheoretically reduce contention on the medium, in reality there canstill be uncontrollable interference from overlapping service areas.

The EDCA mechanism provides differentiated, distributed access bymapping eight different user priorities (UPs) to four access categories(ACs). The AC is derived from the UPs as shown below in Table 2, whichreflects information from Table 9-1 of IEEE Std 802.11™-2012.

TABLE 2 UP-to-AC mappings UP (Same as 802.1D user 802.1D DesignationPriority priority) designation AC (informative) Lowest 1 BK AC_BKBackground 2 — AC_BK Background 0 BE AC_BE Best Effort

3 4 EE CL AC_BE AC_VI Best Effort Video 5 VI AC_VI Video 6 VO AC_VOVoice Highest 7 NC AC_VO Voice

The UP values are in the range of 0-7, the same as the values definedfor 802.1D user priorities (thereby simplifying the mapping). These userpriorities were established for layer 2 data link frame prioritizationin alignment with earlier class of service (CoS) standards including802.1D (based on work done in 802.1p). The 802.1D designations arelisted as follows: BK=Background, BE=Best Effort, EE=Excellent Effort,CL=Controlled Load, VI=Video (<100 ms delay), VO=Voice (<10 ms delay),and NC=Network Control. User priority 0 is placed into the Best EffortAC instead of the Background AC to preserve backward compatibility withnon-QoS stations since the IEEE considers QoS functionality optional.

The WiFi Alliance (WFA) defined its WiFi MultiMedia (WMM) certificationprogram called WMM-Admission Control (WMM-AC) to ensure that devicesrequiring QoS (e.g., for VoIP) are only admitted into the network ifsufficient resources are available. For example, a WMM client caninclude a “Traffic Specification” (TSPEC) in a signaling request to theAP before sending traffic flows of a specific AC type, such as voice.

IEEE 802.11u has defined standards for “Interworking with ExternalNetworks” such as those managed by 3GPP MNOs. The 802.11u amendmentdescribes methods for WLAN network discovery and selection, QoS mappingfrom external networks, and prioritized WLAN access for emergencyservices (e.g., for first responders). The WiFi Alliance has adoptedsome features of 802.11u network discovery and selection into theirHotspot 2.0 “Passpoint” certification program and the 802.11u QoSenhancements may be addressed in future Passpoint releases.

With respect to QoS mapping, 802.11u provides QoS mapping forsubscription service provider networks (SSPNs) and other externalnetworks that may have their own layer-3 end-to-end packet markingpractice (e.g., differentiated services code point (DSCP) usageconventions). Therefore, a way to remap the layer-3 service levels to acommon over-the-air service level is necessary. The QoS map providesstations and access points with a mapping of network-layer QoS packetmarking (e.g., DSCP) to 802.11e UPs.

For the downlink, at the AP, DSCP values are mapped to EDCA UPs. Thenon-AP station 802.11 (STA) may also use TSPEC and TCLAS elements in anadd traffic stream (ADDTS) request frame to setup a traffic stream inthe WLAN. In this method, the UP is specified in the trafficclassification (TCLAS) element. The policy used by the AP to choose aspecific method to map frames to user priorities is outside the scope of802.11.

For the uplink, at the non-AP STA, external QoS parameters are mapped toIEEE 802.11 QoS parameters, e.g., DSCP to IEEE 802.11 UP and in turn toEDCA ACs. This mapping helps the non-AP STA to construct correct QoSrequests to the AP, e.g., ADDTS Request, and to transmit frames at thecorrect priority. Standards do not specify how a UE sets the DSCP valuefor uplink packets, if at all. UE 102 may, for instance, use the valuereceived in the corresponding downlink packet for the correspondingflow.

Table 3, which reflects information from IEEE Std 802.11™-2012 TableV-1, shows examples of differentiated services (DiffServ) per hopbehavior (PHB) and DSCP mappings for 3GPP UMTS/GPRS traffic classes and802.11e AC and UP. The mapping of the DSCP to 3GPP UMTS/GPRS trafficclass is available in Global System for Mobile Association (GSMA) IR.34v4.6, while IR.34 v9.0 adds the Evolved Packet System (EPS) QoS ClassIdentifier (QCI) mappings.

TABLE 3 Mapping table of DSCP to 3GPP QoS Information and EDCA ACs QoSRequirement on GPRS Roaming Exchange MSDU EDCA UP (as 3GPP QoSInformation DiffServ Max Max MSDU Error Access in IEEE Traffic Class THPPHB DSCP Delay Jitter Loss Ratio Category 802.ld) Conversational N/A EF101110  20 ms 5 ms 0.5% 10⁻⁶ AC_VO 7, 6 Streaming N/A AF4₁ 100010  40 ms5 ms 0.5% 10⁻⁶ AV_VI 5, 4 Interactive 1 AF3₁ 011010 250 ms N/A 0.1% 10⁻⁸AC_BE 3 2 AF2₁ 010010 300 ms N/A 0.1% 10⁻⁸ AC_BE 3 3 AF1₁ 001010 350 msN/A 0.1% 10⁻⁸ AC_BE 0 Background N/A BE 000000 400 ms N/A 0.1% 10⁻⁸AC_BK 2, 1

Table 4 may be constructed for EPC-based networks and reflectsinformation from GSMA IR.34 v9.0.

TABLE 4 2G/3G/EPS QOS information and their mapping to DSCP values EPSQoS Information IP transport Signaling Diffserf QCI Traffic Class THPindication PHB DSCP 1 Conversational N/A N/A EF 101110 2 3 4 StreamingN/A N/A AF41 100010 5 Interactive 1 Yes AF31 011010 (see note) 6 No AF32011100 7 2 No AF21 010010 8 3 No AF11 001010 9 Background N/A N/A BE000000

IETF draft-kaippallimalil-netext-pmip-qos-wife-01, “Mapping PMIP Qualityof Service in WiFi Network,” outlines a recommended mapping between 3GPPQCI, DSCP, and 802.11e Access Category (AC) as shown below in Table 5.

TABLE 5 QCI DSCP 802.11e AC Example 3GPP service 1 EF 3 AC_VOconversational voice 2 EF 3 AC_VO conversational video 3 EF 3 AC_VOreal-time gaming 4 AF41 2 AC_VI buffered streaming 5 AF31 2 AC_VI IMSsignaling 6 AF31 2 AC_VI buffered streaming 7 AF21 0 AC_BE interactivegaming 8 AF11 0 AC_BE web access 9 BE 1 AC_BK e-mail

Although the WFA has adopted portions of 802.11u for network discoveryand selection as part of the Hotspot 2.0 initiative and itscorresponding Passpoint certification program, the QoS mapping standardshave not been included to date. Hotspot 2.0 refers to an approach topublic access Wi-Fi by the WFA allowing devices to automatically join aWi-Fi subscriber service.

Given the current gaps of the conventional QoS techniques as eluded toabove, there may be a need for adjustments that enable greater adoptionof WLAN QoS controls, especially in light of the increased deployment ofintegrated small cell and WiFi networks. Defined below are extensions toEAP and Diameter for conveying uplink “WLAN QoS” parameters (e.g., QoSparameters for WiFi) to be applied by the UE. As further describedbelow, EAP and Diameter messages may further be extended such that themessages may be interpreted by the TWAN enroute between the UE and 3GPPAAA server, thereby allowing the TWAN to set corresponding QoS fordownlink traffic to the UE. Referring generally to FIGS. 2 and 3A-D, foroffloaded or EPC-routed traffic, the 3GPP AAA server 107 may provide theUE 102 with uplink 802.11e user priority (UP) preferences via extendedEAP signaling based on HSS 109 subscription information. The TWAN 101may also set the downlink 802.11e UP based on information from theextended EAP and Diameter messages.

In an example embodiment, QoS levels are globally configured in the TWAN101 (e.g., see FIG. 2). In another example embodiment, QoS levels aredefined per subscriber based on information stored in the HSS 109 (e.g.,see FIGS. 3A-D).

For example, a “WLAN QoS” attribute may be implemented in an EAP-AKA′protocol. As stated in Solution 9 of 3GPP TR 23.852, which isincorporated by reference as if the disclosure of which is set forth inits entirety herein: “Between the UE and the TWAN/Authenticator, the newinformation is sent via EAPoL (IEEE 802.1X). Between theTWAN/Authenticator and the 3GPP AAA Server, the EAP-AKA′ payload istransported within Diameter messages. The principle is that the TWAN canread the parameters sent by the UE from the EAP messages, but cannotmodify them, i.e., EAP messages are integrity protected, but notencrypted. When the TWAN needs to send a parameter to the UE, it does soindirectly by inserting the parameter in the Diameter message to the3GPP AAA Server. Then the 3GPP AAA Server relays the parameter in thesubsequent EAP message to the UE.”

Referring in particular to FIG. 2, an example system 200 includes the UE102, the TWAN 101, the 3GPP AAA server 107, and the HSS 109. It will beappreciated that the example system 200 is simplified to facilitatedescription of the disclosed subject matter and is not intended to limitthe scope of this disclosure. Other devices, systems, and configurationsmay be used to implement the embodiments disclosed herein in additionto, or instead of, a system instead of the system 200, and all suchembodiments are contemplated as within the scope of the presentdisclosure.

Referring to FIG. 2, in accordance with the illustrated embodiment, at202, the UE 102 may store uplink (UL) WiFi QoS policies. At 204, theTWAN 101 may store uplink and downlink (DL) WiFi QoS policies. The QoSpolicies, which may include parameters or attributes, may be staticallyconfigured in the TWAN 101 and be subsequently updated via an OAM server(not shown). At 206, the UE 102 may attach to the TWAN 101 via an 802.11communication. At 208, the UE 102, TWAN 101, 3GPP AAA server 107, andHSS 109 may go through a process of authentication onto a network. Thus,the UE 102 may be authenticated at 208. At 210, the TWAN 101 may send anEAP over LAN (EAPoL) message to the UE 102. The message may include anEAP request. At 212, the UE 102 may send an EAP response to the TWAN101. In accordance with the illustrated embodiment, at 214, the TWAN101, inserts one or more TWAN UL QoS parameters in a Diameter message.The one or more QoS parameters may be subsequently sent to the UE 102 inan extended EAP message. At 216, the diameter message that includes theone or more QoS parameters is sent to the 3GPP AAA server 107. Thediameter message may include an AVP (“Attribute Value Pair”) parameterthat conveys the TWAN QoS parameters as described herein.

Still referring to FIG. 2, in accordance with the illustrated example,at 218, the 3GPP AAA server 107 relays the TWAN UL QoS parameters to theUE 102 in an extended EAP message. For example, at 220, the 3GPP AAAserver 107 may send an extended diameter message to the TWAN 101 thatincludes the TWAN QoS parameters. Thus, the TWAN 101, which also bereferred to as a first or TWAN server 101, may receive a message thatindicates a WLAN QoS parameter. The message may be formatted inaccordance with a diameter message. At 222, the TWAN 101 can send anEAPoL message, in particular an EAP request message, to the UE 102 thatincludes the TWAN QoS parameters. Thus, the TWAN 101 may insert the WLANQoS parameter into an extended extensible authentication protocol (EAP)message, thereby providing a QoS policy specified by the MNO to the UE102. In accordance with the illustrated example, the QoS policy is aglobal policy that applies to a plurality of user equipment's in theTWAN 101. In response to the request, the UE 102 may send an EAPresponse message to the TWAN 101, at 223. At 226, the UE 102, TWAN 101,and 3GPP AAA server may perform an EAP notification. At 228, inaccordance with the illustrated example, a diameter message, inparticular an EAP success message, is sent to the TWAN 101 from the 3GPPAAA server 107. At 230, an EAPoL message, in particular the EAP successmessage, is sent to the UE 102 from the TWAN 101. At 232, the UE 102 mayset an UL 802.11e MAC marking per the QoS mapping. Thus, the UE 102 mayset a user priority for WLAN uplink traffic flows according to the WLANQos policy. Thereafter, the UE 102 may provide data to the TWAN 101based on the WLAN QoS policy. Similarly, at 234, the TWAN 101 may set aDL 802.11e MAC marking per the QoS mapping. Thus, the TWAN 101 may set auser priority for WLAN downlink traffic flows in accordance with theWLAN QoS policy. Thereafter, the TWAN 101 may provide data to the UE 102in accordance with the WLAN QoS policy. The HSS 109 may store QoSpolicies specified by the MNO.

As discussed herein, it should be understood that the entitiesperforming the steps illustrated in FIG. 2 are logical entities that maybe implemented in the form of software (e.g., computer-executableinstructions) stored in a memory of, and executing on a processor of, adevice, server, or computer system such as those illustrated in FIG. 4Bor FIG. 4C. That is, the method(s) illustrated in FIG. 2 may beimplemented in the form of software (e.g., computer-executableinstructions) stored in a memory of a computing device, such as thedevice or computer system illustrated in FIG. 4B or FIG. 4C, whichcomputer executable instructions, when executed by a processor of thecomputing device, perform the steps illustrated in FIG. 2.

Referring now to FIG. 3A-D, an example system 300 includes the UE 102,the TWAN 101, the 3GPP AAA server 107, the HSS 109, the PGW 108, and anpolicy and charging rules function (PCRF) 99. It will be appreciatedthat the example system 300 is simplified to facilitate description ofthe disclosed subject matter and is not intended to limit the scope ofthis disclosure. Other devices, systems, and configurations may be usedto implement the embodiments disclosed herein in addition to, or insteadof, a system instead of the system 300, and all such embodiments arecontemplated as within the scope of the present disclosure. Inaccordance with the illustrated embodiment, the 3GPP AAA Server 107 maysignal the QoS preference to the TWAN 101 based on thesubscriber-specific WiFi QoS information provided by the HSS 109. Asfurther described below with reference to FIGS. 3A-D,subscriber-specific QoS parameters may be stored in the HSS 109,conveyed to the 3GPP AAA Server 107, and sent to the UE 102 via the 3GPPAAA Server 107 using extensions to the EAP protocol as described herein.Further, the parameters, and thus the messages, may be monitored by theTWAN 101 enroute to the UE 102.

Referring in particular to FIG. 3A, at 302, in accordance with anexample embodiment, the UE 102 may attach to the TWAN 101 via an 802.11communication. At 304, the UE 304 may send an EAPoL start message to theTWAN 101. In response, at 306, an authentication may be initiated. At308, the 3GPP AAA server 107 may indicate a preference for anon-seamless WLAN offload (NSWO). The NSWO preference may be based on aWLAN QoS policy for a subscriber and/or a flow WLAN QoS policy. At 310,the 3GPP AAA Server 107 sends an AKA′ notification to the UE 102. Thenotification may include, and thus may indicate, the preference forNSWO, which may be per a subscriber WLAN QoS and/or a flow WLAN QoS. At312, in accordance with the illustrated embodiment, the TWAN 101, and inparticular a signaling sniffer of the TWAN 101, sniffs (interprets) EAPsignaling and stores relevant subscription information at the TWAN 101.For example, TWAN 101 may monitor EAP messages between the UE 102 andthe 3GPP AAA server 107, which may also be referred to as a secondserver. Example subscription information includes, without limitation,an NSWO preference and a WLAN QoS policy. The Signaling Sniffer may beimplemented as a separate logical function while being implemented aspart of the TWAN 101. At 314, the authentication, for instance theauthentication of the UE 102, concludes.

Referring now to FIG. 3B, in accordance with an alternative embodiment,at 316, the UE 102 may send an EAPoL start message to the TWAN 101. Inresponse, the TWAN 101 may send an EAPoL request message to the UE 102(at 318). At 320, the UE 102 may send an EAPoL response message to theTWAN 101. At 322, the TWAN 101 may send a diameter message to the 3GPPAAA Server. The diameter message may include the identity of the UE 102associated with the EAP response and an identity of the access network.Thus, the TWAN 101 may send a diameter message to the 3GPP AAA server107, and the diameter message may be indicative of an identity of the UE102. At 324, the 3GPP AAA server 107 requests information from the HSS109. For example, the information may include a WLAN QoS policy that isspecific to the UE 102 based on subscriber information associated withthe UE 102. Alternatively, the 3GPP AAA server 107 may providepreviously stored preferences, for instance during an example fastre-authentication, for NSWO. The information may include the QoS policy,which may be based on the subscriber (e.g., a user of the UE 102 and/orthe UE 102 itself) or the flow, for example. At 326, the 3GPP AAA server107 sends a diameter message to the TWAN 101. The message may includethe retrieved and/or stored information from 324. At 328, in accordancewith the illustrated example, the TWAN 101 sniffs the EAP signaling andstores relevant subscription information in the TWAN 101. Thus, the TWAN101 may monitor EAP messages between the UE 102 and the 3GPP AAA server107. Based on the monitored EAP messages and the identity of the UE 102,the TWAN 101 may identify a WLAN QoS policy associated with the UE 102.Example subscription information may include, without limitation, theNSWO preference and the WLAN QoS policy, which may be specific to the UE102 based on subscriber information associated with the UE. At 330, theTWAN 101 may send an EAPoL request message to the UE 102. The messagemay include the identified WLAN QoS policy. Thus, the TWAN 101 may sendthe identified WLAN QoS policy to the UE 102, for instance via an EAPmessage. The QoS policy may be retrieved via the HSS 109. The UE 102 maysend an EAPoL response message to the TWAN 101, at 332. At 334, the TWAN101 may send a diameter message that includes the EAP response to the3GPP AAA server 107. At 336, the 3GPP AAA server 107 may send a diametermessage that includes an EAP success message to the TWAN 101. At 338,the TWAN 101 may relay the EAP success message in an EAPoL message thatis sent to the UE 102.

Referring now to FIG. 3C, in accordance with another alternativeembodiment, at 340, the UE 102 may send an EAPoL start message to theTWAN 101. In response, the TWAN 101 may send an EAPoL request message tothe UE 102 (at 342). At 344, the UE 102 may send an EAPoL responsemessage to the TWAN 101. At 346, the TWAN 101 may send a diametermessage to the 3GPP AAA Server 107. The diameter message may include anEAP request message that may include subscription data. At 350, the TWAN101 may send an EAPoL request message to the UE 102. The UE 102 may sendan EAPoL response message to the TWAN 101, at 352. At 354, the TWAN 101may send a diameter message that includes the EAP response to the 3GPPAAA server 107. At 356, in accordance with the illustrated example, the3GPP AAA server 107 requests (retrieves) information from the HSS 109 ifthe information was not previously stored. At 358, the 3GPP AAA server107 sends a diameter message to the TWAN 101. The message may includethe retrieved information from 356. The retrieved information mayinclude, presented by way of example, subscription information, the APNidentity, and the WLAN QoS, which may be subscriber based and/or flowbased. At 360, the TWAN 101 retrieves subscription data from thereceived diameter message, and in particular the new diameter AVP. TheTWAN 101 may store relevant WLAN QoS subscription information in theTWAN 101. At 362, the TWAN 101 may send an EAPoL request message to theUE 102. The EAPoL request message may include the WLAN QoS policy, whichmay be subscriber based and/or flow based. For example, in some cases,the WLAN QoS policy is specific to the UE 102. Thus, the TWAN 101 mayalso set a user priority for WLAN downlink traffic flows destined forthe UE 102 in accordance with the WLAN QoS policy. The UE 102 may sendan EAPoL response message to the TWAN 101, at 364. At 366, the TWAN 101may send a diameter message that includes the EAP response to the 3GPPAAA server 107. At 368, the 3GPP AAA server 107 may send a diametermessage that includes an EAP success message to the TWAN 101. At 370,the TWAN 101 may relay the EAP success message in an EAPoL message thatis sent to the UE 102. Thus, the UE 102 may be authenticated with aserver that is controlled by an MNO. Based on the authentication, the UE102 may receive a message that indicates a WLAN QoS policy. In variousexample embodiments, the message is formatted in accordance with anextended EAP message.

Referring now to FIG. 3D, after any of the authentications describedabove, a default bearer may be established between the TWAN 101 and theHSS 109, at 372. Alternatively, at 374, a dedicated bearer may beestablished between the TWAN 101 and the HSS 109. At 376, the UE 101 mayset the UL 802.11e MAC marking per the QoS mapping. Thus, the UE 102 mayset a user priority for WLAN uplink traffic flows according to the WLANQoS policy specified by the MNO. The UE 102 may thus provide data to theTWAN 101 based on the WLAN QoS policy. At 378, the TWAN 101 may set theDL 802.11e MAC marking per the QoS mapping. Thus, the TWAN 101 may set auser priority for WLAN downlink traffic flows destined for the UE 102 inaccordance with the WLAN QoS policy. The TWAN 101 may further providedata to the UE 102 in accordance with the WLAN QoS policy that may bespecified by the MNO.

Thus, as described above, the TWAN 101 may include a signaling snifferthat reads the subscriber-specific “WLAN QoS” Diameter extensionsprovided to the TWAN 101 by the 3GPP AAA Server 107, sniffs thesubscriber-specific “WLAN QoS” EAP extensions provided to the UE 102 bythe 3GPP AAA Server 107, and/or provides the “WLAN QoS” and associatedsubscription information to the WiFi QoS Policy Manager.

Further, for downlink data over the SWw air interface, the TWAN 101 mayset the 802.11e UP for traffic flows based on pre-configured values orbased on an inspection of HSS subscriber info conveyed via the 3GPP AAAserver 107 using extended EAP/Diameter signaling. Pre-configuredpolicies may be used for handling the differentiation of downlink flows.For example, referring to FIG. 2, global flow-based policies matchconfigured packet filters. In accordance with the description relativeto FIGS. 3A-D, using EAP/Diameter with the described “WLAN QoS”extensions, the downlink traffic that is handled is tailored using theWLAN QoS information stored for the user in the HSS 109.

In an example embodiment for uplink data over the SWw air interface, theUE 102 sets the 802.11e UP for traffic flows according to apre-configured operator policy or as signaled by the new mechanismsdescribed above. Pre-configured policies may be used for handling thedifferentiation of uplink flows, e.g., via flow-based policies matchingspecified packet filters. Using EAP with the described “WLAN QoS”extension, the uplink traffic handling may be tailored using the WLANQoS information stored for the user in the HSS 109.

Referring again to FIG. 3D, in some cases, dedicated bearers may beassociated with a default PDN connection and may exhibit specific QoSrequirements that cannot be adequately handled by the defaultconnection. Packets belonging to the dedicated bearer may bedistinguished via packet filters comprising a Traffic Flow Template(TFT). In the TWAN 101, the TFTs may be provided via GTP signaling fromthe PGW 108 and may be used to route uplink packets from the TWAN 101 tothe PGW 108 via the associated dedicated bearer. The PGW 108 may use itsTFTs to route downlink packets to the TWAN 101 via the associateddedicated bearer.

As discussed herein, it should be understood that the entitiesperforming the steps illustrated in FIGS. 3A-D are logical entities thatmay be implemented in the form of software (e.g., computer-executableinstructions) stored in a memory of, and executing on a processor of, adevice, server, or computer system such as those illustrated in FIG. 4Band FIG. 4C. That is, the method(s) illustrated in FIGS. 3A-D may beimplemented in the form of software (e.g., computer-executableinstructions) stored in a memory of a computing device, such as thedevice or computer system illustrated in FIG. 4B or FIG. 4C, whichcomputer executable instructions, when executed by a processor of thecomputing device, perform the steps illustrated in FIGS. 3A-D.

Disclosed below are more details with regard to 3GPP architecture thatprovides cellular LTE and Trusted WLAN access to an EPC. Under currentpractices, mobile network operators (MNOs) typically employ WiFi foroffloading “best effort” Internet traffic from their cellular and corenetworks. However, increased interest in operator deployment of “smallcells” and “carrier WiFi” is expected to encourage MNOs to seek betterinter-operability across local cellular and WiFi networks. Generally,“small cells” refer to localized geographic areas providing wirelessnetwork access via operator-licensed spectrum using 3GPP-definedcellular Radio Access Technologies (RATs). Although offloaded traffic isdiscussed herein, it is contemplated that devices that may primarily useWiFi communication may practice the WLAN QoS via EAP/Diameter asdisclosed herein.

As operators adopt “carrier WiFi” to optimize their networks and reduceexpenses, it is expected that there will be a greater deployment of“Trusted” WLAN Access Networks (TWAN) that can interface directly withan operator's Mobile Core Network (MCN). Similarly, it is expected thatthere will be greater integration of MNO deployed small cell and WiFiaccess networks within common geographical areas such as high-trafficurban metropolitan hotspot locations. Such integration is motivated bythe growing number of smartphones that support both cellular and WiFiaccess.

In this context, the term “trusted WLAN (TWAN) access” refers to thecircumstances wherein appropriate measures have been taken to safeguardthe EPC from access via the WLAN. Such measures are left to thediscretion of the MNO and may, for example, include establishment of atamper-proof fiber connection between the WLAN and EPC, or establishmentof an IPSec security association between the WLAN and a Security Gatewayat the EPC edge. In contrast, if the WLAN access is deemed “untrusted,”the WLAN may interface with an evolved Packet Data Gateway (ePDG) at theEPC edge, and the ePDG must establish an IPSec security associationdirectly with each UE accessing the EPC through the WLAN.

FIG. 4A is a diagram of an example communication system 10 in which oneor more disclosed embodiments may be implemented. FIG. 4A depicts a 3GPParchitecture that provides cellular LTE and Trusted WLAN access to EPC119. As described in section 16.1.1 of 3GPP Technical Specification (TS)23.402, the contents of which are hereby incorporated herein byreference, when WLAN AN 113 is considered trusted by the operator, theTrusted WLAN Access Network (TWAN) 101 can be connected to EvolvedPacket Core (EPC) 119 via the STa interface 104 toward the 3GPP AAAServer 107 for authentication, authorization, and accounting via the S2ainterface 106 toward PDN Gateway (PGW) 108 for user plane traffic flows.An alternate path from TWAN 101 to a local IP network 111 (i.e.,intranet) and/or directly to the Internet 111 is also shown.

3GPP LTE access network 121 (i.e., evolved Node B) is connected to EPC119 via S1-MME interface 123 which provides a communication path withMobility Management Entity (MME) 125. S1-U interface 127 provides acommunication path with Serving Gateway (SGW) 129, which interfaces withPDN Gateway (PGW) 108 via S5 interface 131.

A “local gateway” function (L-GW) 133 provides small cell LTE access,e.g., for Home eNB (HeNB) deployments. Similarly, a “HeNB Gateway” (HeNBGW) 135 may be used to concentrate control plane signaling for multipleHeNBs toward MME 125 and could also be used to handle HeNB user planetraffic toward SGW 129. A HeNB Management System (HeMS) 137 provides“plug-and-play” auto configuration of HeNBs based on TR-069 standardspublished by the broadband forum (BBF) and adopted by 3GPP. A securitygateway (SeGW) 139 provides trusted access to EPC 119 via HeNB GW 135.

WLAN AN 113 comprises one or more WLAN Access Points (APs). An AP (notshown) terminates UE 102 WLAN IEEE 802.11 link via SWw interface 156.The APs may be deployed as standalone APs or as “thin” APs connected toa Wireless LAN Controller (WLC) using, for example, the IETF CAPWAPprotocols.

TWAG 117 terminates the GTP-based S2a interface 106 with the PGW 108 andmay act as the default IP router for UE 102 on its WLAN access link. Italso may act as a DHCP server for UE 102. TWAG 117 typically maintains aUE MAC address association for forwarding packets between UE 102 (viathe WLAN AP) and the associated S2a interface 106 GTP-U tunnel (via thePGW 108).

Trusted WLAN AAA Proxy (TWAP) 115 terminates the Diameter-based STainterface 104 with the 3GPP AAA Server 107. TWAP 115 relays the AAAinformation between the WLAN AN 113 and 3GPP AAA Server 107 (or Proxy incase of roaming). TWAP 115 can inform TWAG 117 of the occurrence oflayer 2 attach and detach events. TWAP 115 establishes the binding of UEsubscription data (including IMSI) with UE MAC address and can providesuch information to TWAG 117.

In existing systems, UE 102 can leverage USIM features for both 3GPP andnon-3GPP WLAN access. Processing for authentication and security isdescribed in section 4.9.1 of 3GPP TS 23.402, the contents of which arehereby incorporated by reference in their entirety. As describedtherein, non-3GPP access authentication, such as that which takes placevia WLAN AN 113, defines the process that is used for access control andthereby permits or denies a subscriber from attaching to and using theresources of a non-3GPP IP access which is interworked with the EPC 119.Non-3GPP access authentication signaling is executed between UE 102 andthe 3GPP AAA server 107 and HSS 109. The authentication signaling maypass through AAA proxies.

Trusted 3GPP-based access authentication is executed across STainterface 104. The 3GPP based access authentication signaling is basedon IETF protocols, e.g., Extensible Authentication Protocol (EAP). STainterface 104 and Diameter application are used for authenticating andauthorizing UE 102 for EPC 119 access via trusted non-3GPP accesses.3GPP TS 29.273, the contents of which are hereby incorporated byreference in its entirety, describes the standard TWAN procedurescurrently supported on STa interface 104.

For EPC 119 access via GTP-based TWAN 101, the IPv4 address and/or IPv6prefix is allocated to UE 102 when a new PDN connection is establishedwith EPC 119 over TWAN 101. A separate IP address may also be allocatedby the TWAN 101 for local network traffic and/or direct Internetoffload.

For PDN connectivity through EPC 119 via TWAN 101, TWAN 101 receivesrelevant PDN information via EAP/Diameter or WLCP signaling. TWAN 101may request an IPv4 address for UE 102 from PGW 108 via the GTP CreateSession Request. The IPv4 address is delivered to TWAN 101 during theGTP tunnel establishment via the GTP Create Session Response. When UE102 requests an IPv4 address for PDN connectivity via DHCPv4, the TWAN101 delivers the received IPv4 address to the UE 102 within DHCPv4signaling. Corresponding procedures are also defined for IPv6.

For 3GPP LTE access, the UE 102 automatically triggers a PDN connectionas part of its initial attachment to the EPC 119. UE 102 maysubsequently establish additional PDN connections as needed.

The primary purpose of the attach procedure is for UE 102 to registerwith the network in order to receive services for which it hassubscribed to. The attach procedure confirms the user's identity,identifies the services it is allowed to receive, establishes thesecurity parameters (e.g., for data encryption), and notifies thenetwork of the UE 102 initial location (e.g., in case it needs to bepaged). Also, to support the “always-on” network connectivity expectedby today's users, the LTE standards specify establishment of a defaultPDN connection as part of the Attach procedure. The radio resources forthis default connection may be released during periods of inactivity,however the rest of the connection remains intact and the end-to-endconnection can be quickly re-established by reassigning the radioresources in response to UE 102 service requests.

When UE 102 attempts to attach to EPC 119 via an (H)eNB LTE network 121,it first establishes an RRC connection with the (H)eNB LTE network 121and encapsulates the Attach Request within the RRC signaling. (H)eNB LTEnetwork 121 then forwards the attach request to MME 125 via S1-APsignaling on S1-MME interface 123. MME 125 retrieves subscriptioninformation from HSS 109 via the Sha interface 126 in order toauthenticate UE 102 and allow attachment to EPC 119.

After successfully authenticating the UE 102, MME 125 selects SGW 129(e.g., based on proximity to the (H)eNB LTE network 121), and alsoselects PGW 108 (e.g., based on the default APN retrieved from HSS 109or a specific APN requested by UE 102). MME 125 communicates with SGW129 over S11 interface 124 and requests creation of the PDN connection.SGW 129 executes the signaling to establish a GTP user plane tunnel withthe designated PGW 108 over the S5 interface 131.

“GTP control” signaling takes place within the S1-AP protocol betweenthe MME 125 and (H)eNB 121. This ultimately leads to the establishmentof a GTP user plane tunnel on the S1-U interface 127 between (H)eNB 121and SGW 129. The path for the PDN connection between the UE 102 and PGW108 is thus completed through the (H)eNB 121 and SGW 129.

The end-to-end path for the PDN connection between the UE 102 and PGW108 is thus completed through (H)eNB 121 and SGW 129.

In systems where communications take place via TWAN 101, UE 102authentication and EPC 119 attachment is accomplished via EAP signalingbetween UE 102 and 3GPP AAA Server 107.

The PDN connectivity service is provided by the point-to-pointconnectivity between UE 102 and the TWAN 101, concatenated with S2abearer(s) 106 between TWAN 101 and PGW 108. Unlike the LTE model, theWLAN radio resources are “always-on” from an EPC perspective. In otherwords, any power-saving optimizations are handled transparently usingIEEE 802.11 procedures within the WLAN.

When UE 102 attempts to attach to EPC 119 via TWAN 101, it firstestablishes a Layer 2 connection with the WLAN AN 113 and encapsulatesEAP messages within EAPoL signaling. WLAN AN 113 forwards the EAPmessages to TWAP 115 which encapsulates the messages within Diametersignaling and forwards the messages to 3GPP AAA Server 107 via the STainterface 104. 3GPP AAA server 107 retrieves subscription informationfrom the HSS 109 via the SWx interface 128 in order to authenticate UE102 and allow attachment to EPC 119.

For 3GPP Release 11, 3GPP AAA Server 107 also provides TWAN 101 withinformation via STa interface 104 for establishing a PDN connection tothe default PDN provisioned in the HSS 109. TWAN 101 then exercises GTPcontrol plane (GTP-C) and user plane (GTP-U) protocols over S2ainterface 106 directly toward PGW 108, thereby completing the PDNconnection between UE 102 and PGW 108 through TWAN 101.

For 3GPP Release 12, the SaMOG phase-2 work item defines additionalprocedures for UE-initiated PDN connectivity, multi-PDN connectivity,and seamless inter-system handover. For the case of single-PDN capableTWAN scenarios, EAP extensions are defined to support UE-initiated PDNrequests and seamless inter-system handover requests. For the case ofmulti-PDN capable TWAN scenarios, a WLAN Control Protocol (WLCP) isdefined between the UE and TWAN to enable one or more UE PDN connectionrequests and seamless handover procedures. However, separate proceduresare still utilized between the UE and 3GPP AAA Server for UEauthentication.

FIG. 4B is a system diagram of an example user equipment, such as UE102. Example user equipment (UE) includes, but is not limited to, amobile station, a fixed or mobile subscriber unit, a pager, a cellulartelephone, a personal digital assistant (PDA), a smartphone, a laptop, anetbook, a personal computer, a wireless sensor, consumer electronics,wearable devices, or the like. As shown in FIG. 4B, UE 102 may include aprocessor 32, a transceiver 34, a transmit/receive element 36, aspeaker/microphone 38, a keypad 40, a display/touchpad 42, non-removablememory 44, removable memory 46, a power source 48, a global positioningsystem (GPS) chipset 50, and other peripherals 52. It will beappreciated that UE 102 may include any sub-combination of the foregoingelements while remaining consistent with an embodiment. UE 102 may be adevice that uses the disclosed systems, devices, and methods for WLANQoS via EAP/Diameter.

The processor 32 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 32 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the UE 102 to operate in a wirelessenvironment. The processor 32 may be coupled to the transceiver 34,which may be coupled to the transmit/receive element 36. While FIG. 4Bdepicts the processor 32 and the transceiver 34 as separate components,it will be appreciated that the processor 32 and the transceiver 34 maybe integrated together in an electronic package or chip. The processor32 may perform application-layer programs (e.g., browsers) and/or radioaccess-layer (RAN) programs and/or communications. The processor 32 mayperform security operations such as authentication, security keyagreement, and/or cryptographic operations, such as at the access-layerand/or application layer for example.

The transmit/receive element 36 may be configured to transmit signalsto, or receive signals from, WLAN AN 113 or (H)eNB 121. For example, inan embodiment, the transmit/receive element 36 may be an antennaconfigured to transmit and/or receive RF signals. The transmit/receiveelement 36 may support various networks and air interfaces, such asWLAN, WPAN, cellular, and the like. In an embodiment, thetransmit/receive element 36 may be an emitter/detector configured totransmit and/or receive IR, UV, or visible light signals, for example.In yet another embodiment, the transmit/receive element 36 may beconfigured to transmit and receive both RF and light signals. It will beappreciated that the transmit/receive element 36 may be configured totransmit and/or receive any combination of wireless or wired signals.

In addition, although the transmit/receive element 36 is depicted inFIG. 4B as a single element, UE 102 may include any number oftransmit/receive elements 36. More specifically, the UE 102 may employMIMO technology. Thus, in an embodiment, the UE 102 may include two ormore transmit/receive elements 36 (e.g., multiple antennas) fortransmitting and receiving wireless signals.

The transceiver 34 may be configured to modulate the signals that are tobe transmitted by the transmit/receive element 36 and to demodulate thesignals that are received by the transmit/receive element 36. As notedabove, UE 102 may have multi-mode capabilities. Thus, transceiver 34 mayinclude multiple transceivers for enabling UE 102 to communicate viamultiple RATs, such as UTRA and IEEE 802.11, for example.

Processor 32 may access information from, and store data in, any type ofsuitable memory, such as non-removable memory 44 and/or removable memory46. Non-removable memory 44 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. Removable memory 46 may include a subscriber identity module(SIM) card, a memory stick, a secure digital (SD) memory card, and thelike. In other embodiments, the processor 32 may access informationfrom, and store data in, memory that is not physically located on UE102, such as on a server or a home computer. The processor 32 may beconfigured to control lighting patterns, images, or colors on thedisplay or indicators 42 in response to whether the WLAN QoS viaEAP/Diameter in some of the embodiments described herein are successfulor unsuccessful, or otherwise indicate the status of QoS or theprocesses for implementing QoS (e.g., FIGS. 2-3D with associated text).

The processor 32 may receive power from the power source 48, and may beconfigured to distribute and/or control the power to the othercomponents in UE 102. The power source 48 may be any suitable device forpowering UE 102. For example, the power source 48 may include one ormore dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc(NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solarcells, fuel cells, and the like.

The processor 32 may also be coupled to the GPS chipset 50, which isconfigured to provide location information (e.g., longitude andlatitude) regarding the current location of UE 102. It will beappreciated that UE 102 may acquire location information by way of anysuitable location-determination method while remaining consistent withan embodiment.

The processor 32 may further be coupled to other peripherals 52, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 52 may include anaccelerometer, an e-compass, a satellite transceiver, a sensor, adigital camera (for photographs or video), a universal serial bus (USB)port, a vibration device, a television transceiver, a hands freeheadset, a Bluetooth® module, a frequency modulated (FM) radio unit, adigital music player, a media player, a video game player module, anInternet browser, and the like.

FIG. 4C is a block diagram of an exemplary computing system 90 on which,for example, devices within or connected with the communication system10 of FIG. 4A and FIG. 1 may be implemented. Computing system 90 maycomprise a computer or server and may be controlled primarily bycomputer readable instructions, which may be in the form of software,wherever, or by whatever means such software is stored or accessed. Suchcomputer readable instructions may be executed within central processingunit (CPU) 91 to cause computing system 90 to do work. In many knownworkstations, servers, and personal computers, central processing unit91 is implemented by a single-chip CPU called a microprocessor. In othermachines, the central processing unit 91 may comprise multipleprocessors. Coprocessor 81 is an optional processor, distinct from mainCPU 91 that performs additional functions or assists CPU 91. CPU 91and/or coprocessor 81 may receive, generate, and process data related tothe disclosed systems and methods for WLAN QoS via EAP/Diameter, such asreceiving appropriate diameter messages or EAP response or requestmessages.

In operation, CPU 91 fetches, decodes, and executes instructions, andtransfers information to and from other resources via the computer'smain data-transfer path, system bus 80. Such a system bus connects thecomponents in computing system 90 and defines the medium for dataexchange. System bus 80 typically includes data lines for sending data,address lines for sending addresses, and control lines for sendinginterrupts and for operating the system bus. An example of such a systembus 80 is the PCI (Peripheral Component Interconnect) bus.

Memory devices coupled to system bus 80 include random access memory(RAM) 82 and read only memory (ROM) 93. Such memories include circuitrythat allows information to be stored and retrieved. ROMs 93 generallycontain stored data that cannot easily be modified. Data stored in RAM82 can be read or changed by CPU 91 or other hardware devices. Access toRAM 82 and/or ROM 93 may be controlled by memory controller 92. Memorycontroller 92 may provide an address translation function thattranslates virtual addresses into physical addresses as instructions areexecuted. Memory controller 92 may also provide a memory protectionfunction that isolates processes within the system and isolates systemprocesses from user processes. Thus, a program running in a first modecan access only memory mapped by its own process virtual address space;it cannot access memory within another process's virtual address spaceunless memory sharing between the processes has been set up.

In addition, computing system 90 may contain peripherals controller 83responsible for communicating instructions from CPU 91 to peripherals,such as printer 94, keyboard 84, mouse 95, and disk drive 85.

Display 86, which is controlled by display controller 96, is used todisplay visual output generated by computing system 90. Such visualoutput may include text, graphics, animated graphics, and video. Display86 may be implemented with a CRT-based video display, an LCD-basedflat-panel display, gas plasma-based flat-panel display, or atouch-panel. Display controller 96 includes electronic componentsrequired to generate a video signal that is sent to display 86.

Further, computing system 90 may contain network adaptor 97 that may beused to connect computing system 90 to an external communicationsnetwork 10.

It is understood that any or all of the systems, methods and processesdescribed herein may be embodied in the form of computer executableinstructions (i.e., program code) stored on a computer-readable storagemedium which instructions, when executed by a machine, such as acomputer, server, UE, or the like, perform and/or implement the systems,methods and processes described herein. Specifically, any of the steps,operations or functions described above may be implemented in the formof such computer executable instructions. Computer readable storagemedia include volatile and nonvolatile, removable and non-removablemedia implemented in any method or technology for storage ofinformation, but such computer readable storage media do not includessignals. Computer readable storage media include, but are not limitedto, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disks (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other physical medium which can be used to storethe desired information and which can be accessed by a computer.

In describing preferred embodiments of the subject matter of the presentdisclosure, as illustrated in the Figures, specific terminology isemployed for the sake of clarity. The claimed subject matter, however,is not intended to be limited to the specific terminology so selected,and it is to be understood that each specific element includes alltechnical equivalents that operate in a similar manner to accomplish asimilar purpose.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal languages of the claims.

What is claimed is:
 1. A user equipment comprising: a processor; and amemory coupled with the processor, the memory having stored thereonexecutable instructions that when executed by the processor cause theprocessor to effectuate operations comprising: authenticating with aserver controlled by a mobile network operator (MNO); based on theauthentication, receiving a message that indicates a wireless local areanetwork (WLAN) quality of service (QoS) policy, wherein the messagefurther indicates that the server has preference for non-seamless WLANoffload (NSWO); and receiving downlink traffic flows in accordance withthe WLAN QoS policy and the preference for NSWO.
 2. The user equipmentof claim 1, wherein the message is received from a trusted network(TWAN) server.
 3. The user equipment of claim 2, the operations furthercomprising: providing data to the TWAN server based on the WLAN QoSpolicy.
 4. The user equipment of claim 1, the operations furthercomprising: setting a user priority for WLAN uplink traffic flowsaccording to the WLAN QoS policy.
 5. The user equipment of claim 1,wherein the WLAN QoS policy is stored in a home subscriber server (HSS).6. The user equipment of claim 1, wherein the WLAN QoS policy is appliedto the user equipment based on subscriber information associated withthe user equipment.
 7. A method performed by a user equipment, themethod comprising: authenticating with a server controlled by a mobilenetwork operator (MNO); based on the authentication, receiving a messagethat indicates a wireless local area network (WLAN) quality of service(QoS) policy, wherein the message further indicates that the server hasa preference for non-seamless WLAN offload (NSWO); and receivingdownlink traffic flows in accordance with the WLAN QoS policy and thepreference for NSWO.
 8. The method of claim 7, wherein the message isreceived from a trusted network (TWAN) server.
 9. The method of claim 8,the method further comprising: providing data to the TWAN server basedon the WLAN QoS policy.
 10. The method of claim 7, the method furthercomprising: setting a user priority for WLAN uplink traffic flowsaccording to the WLAN QoS policy.
 11. The method of claim 7, wherein theWLAN QoS policy is stored in a home subscriber server (HSS).
 12. Themethod of claim 7, wherein the WLAN QoS policy is applied to the userequipment based on subscriber information associated with the userequipment.